System and Method for Electronic Document Interaction with External Resources

ABSTRACT

A system and method for electronic document management including: creating an executable document object, wherein the executable document object comprises at least one programmable element; constructing an interaction schema object, wherein each interaction schema comprises: executable logic and a trigger as part of an inbound interaction schema or an outbound interaction schema that associates an external resource with the executable document object; and bundling the interaction schema object with the executable document object. The method further includes: in response to triggering an inbound interaction schema trigger: activating the executable logic of the inbound interaction schema, initiating at least one programmable element of the executable document object, and updating the state of the executable document object; and in response to triggering an outbound interaction schema trigger: activating the executable logic of the outbound interaction schema, and modifying the associated external resource with respect to the state of the executable document object.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/682,898, filed Feb. 28, 2022, which is a continuation of U.S.application Ser. No. 16/940,135, filed Jul. 27, 2020, now U.S. Pat. No.11,314,935, which claims the benefit of U.S. Provisional Application No.62/878,697, filed on Jul. 25, 2019, all of which are incorporated intheir entirety by this reference.

TECHNICAL FIELD

This invention relates generally to the field of electronic documentprocessing, and more specifically to a new and useful system and methodfor electronic document interaction with external resources.

BACKGROUND

Electronic documents (or ‘smart’ documents, or data-driven documents)are computer-managed resources that may have additional functionalitybeyond plain text. This enables the creation of new types of documentswith many added functionalities. Examples of documents may include:automated organization documents, contracts with enforcementcapabilities, transaction documents, policy documents, planningdocuments, authentication and authorization documents, etc.

With more complex functionality, there is a greater need for electronicdocuments to connect and interact with external resources to accomplishcertain desired tasks. Connecting, or exposing a document to externalsystems to draw in data from external resources or to perform actionsand operations on these external resources while ensuring that there isa valid system of record of these operations is an impediment to theadoption and use of electronic documents. Typically, all externalinteractions must be taken into account upon creation of an electronicdocument such that the document has the ability to interact withexternal resources. Having to consider external resources during thecreation of an electronic document thus creates a burdensome laboroverhead for implementation of electronic documents (e.g. electroniccontracts). This may create a barrier to creating, customizing, and/orusing such electronic documents.

Thus, there is a need in the field of electronic document management tocreate a new and useful system and method for configuring the formation,execution, and management of executable documents, for efficientimplementation of interactions with external resources. This inventionprovides such a new and useful system and method.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart representation of a method of a preferredembodiment;

FIG. 2-4 are exemplary screenshots of a user interface;

FIG. 5 is a flowchart representation of one variation of methodsub-steps;

FIG. 6 is a flowchart representation of one variation of methodsub-steps;

FIG. 7 is a schematic of electronic document bundling;

FIG. 8 is a flowchart representation of data flow;

FIG. 9 is a schematic representation of a system of a preferredembodiment;

FIG. 10 is one schematic representation of system interaction;

FIG. 11 is a schematic representation of an embodiment that includes thetemplating system;

FIG. 12 is a schematic representation of a second embodiment thatincludes the templating system;

FIG. 13 is a schematic overview of management system componentsinterfaced with an external resource; and

FIG. 14 is an exemplary system architecture that may be used inimplementing the system and/or method.

DESCRIPTION OF THE EMBODIMENTS

The following description of the embodiments of the invention is notintended to limit the invention to these embodiments but rather toenable a person skilled in the art to make and use this invention.

1. Overview

A system and method for executable electronic document management of oneembodiment can include: creating, managing, and executing electronicdocuments as part of a document package, wherein the document packageincludes the electronic document and interaction schemas that configureand manage connections to external application programming interfaces(APIs). The interaction schemas can include executable logic that defineand control the interactions between the electronic document and theexternal resources. The system and method preferably implement technicalsolutions to constructing and using interaction schemas with anelectronic document. These interaction schemas may be constructed denovo for each implementation. In some variations, the system and methodmay include a template library, wherein interaction schemas associatedwith specific external resources may be stored as interaction schematemplates. Interaction schemas may then be generated and instantiatedwith all necessary user and external resource assets into the documentpackage.

As part of a platform for creating, managing, bundling, and executingelectronic documents, the system and method may comprise: a documentmanagement system, used to create, edit, and remove document packagecomponents; a repository system, that stores electronic documents andall associated components; a templating system, for creation andimplementation of document and interaction schema templates; and anexecution engine, that compiles and executes the electronic document andassociated components.

The system and method function to enable the use and processing ofexternal data with and through the electronic document. Via inboundinteraction schemas, the system and method enables the electronicdocument to be configured to utilize data from resources external to thedocument (e.g. process data from external resources, performcomputations using data from one or more resource(s), or respond toevents by updating and/or utilizing the state of the electronicdocument). Via outbound interaction schemas, the system and methodenables the electronic document to perform actions on or withinresources external to the document (e.g. record/update copies of thedocument, process calculations external to the document, or performtransactions).

The system and method may be implemented as a private, or local network,document platform, wherein one user, or multiple users, may manage andexecute documents locally that access local and remote APIs.Alternatively, the system and method may be implemented as a service,wherein users may “log in” to access tools and templates for electronicdocument management. This service may be as part of a regularly updatedsoftware, cloud service, or similar implementation.

The system and method may provide a number of potential benefits. Thesystem and method are not limited to always providing such benefits, andare presented only as exemplary representations for how the system andmethod may be put to use. The list of benefits is not intended to beexhaustive and other benefits may additionally or alternatively exist.

As one potential benefit, the system and method enables use of templatesto create electronic documents. This may enable a user with little to noprogramming skill to create an electronic document with complexfunctionalities, including, but not limited to, workflows and businessprocesses.

Generally, a user needs to know the appropriate protocols to utilize anAPI. With templates and instantiated interaction schemas, a user mayhave full accessibility to a desired API with no or little knowledge ofappropriate protocols.

As another potential benefit, the system and method may enable quickadditions of API interactions through simple configuration and‘drag-and-drop’ tools.

As part of a management platform, the system and method may enable auser to access multiple APIs using a single login. By logging into theplatform, interaction behind containing all necessary assets may accessdesired APIs.

Additionally, as part of the management platform, the system and methodmay enable association of multiple APIs to single, or multipledocuments, as part of a complex workflow.

2. Method

As shown in FIG. 1 , a method for executable electronic documentmanagement includes: creating an executable document object S110,wherein the executable document object comprises executable programmableelements and optionally natural language elements; constructing aninteraction schema object S120, wherein each interaction schemacomprises: executable logic and a trigger component as part of aninbound interaction schema or an outbound interaction schema thatassociates an external resource with the executable document object; andbundling the interaction schema object with the executable documentobject. Creating an executable document object S110 may include: settingexecutable programmable elements within the executable document object;integrating natural language elements with the programmable elementsS114; and establishing a state for the programmable elements S116,thereby making the programmable elements executable. Constructing aninteraction schema object S120 may include: associating an externalresource with the executable document object S122, generating anexecutable logic for the interaction schema object from a interactionschema template S124, setting a trigger type for the trigger S126, andinstantiating the executable logic of the interaction schema objectS128. The method functions to create and package an executableelectronic document such that external resources may be leveraged forexecution of the electronic document (or the electronic document may beleveraged for an action on, or by, external resources). Thus, the methodfurther includes: in response to triggering an inbound interactionschema trigger: activating the executable logic of the inboundinteraction schema S210, initiating at least one programmable element ofthe executable document object S212, and updating the state of theexecutable document object S214; and in response to triggering anoutbound interaction schema trigger: activating the executable logic ofthe outbound interaction schema S220, and modifying the associatedexternal resource with respect to the state of the executable documentobject S222.

As a method for executable electronic document management, the methodmay be implemented in numerous preferred variations, wherein the methodmay comprise just a single or multiple aforementioned steps orsub-steps, multiple iterations of any steps or sub-steps, and/or inconjunction with additional desired steps. For example, in somevariations, the method further includes building an executable documentobject template and/or creating a interaction schema template, whereinthe object template and interaction schema template may function asprecursor building blocks for creating an executable document objectS110 and constructing interaction schema objects S120.

As a first example implementation, the method may function as part of asingle user management platform, wherein the user may implement allaforementioned steps for electronic document management. The user mayadditionally acquire templates from an internal library of templates, anexternal source (e.g. as part of a software purchase), and/or create newtemplates.

In a second example, the method may be implemented as part of amulti-user management platform. In this example, user-created executabledocument objects may be previously implemented, wherein a new user maythen instantiate the executable document objects as desired. Themulti-user management platform can support users to create multipleelectronic documents. In some cases, components (e.g., interactionschemas) may be shared across different instances of an electronicdocument. In one example for a contract electronic document, multiplecontract participants may each have a “copy” of the document on the samemanagement platform. These copies may then receive status updates froman inbound interaction schema associated with external API (e.g. aweb-trading platform).

In a third example, the method may be provided as a service, e.g. aspart of a ‘pay-to use’ management platform. In this example, externalresources may be already identified. Thus, common external resourceassociations may already be implemented. Additionally, bundling ofcommonly used interaction schemas with specific executable documentobjects may be previously implemented at a template level, such that auser may create an executable document object S110 and construct aninteraction schema object S120 simultaneously.

In a fourth example, the method may be implemented as part of anelectronic contract management platform. In this example, executabledocument objects may function as electronically executable contracts,wherein execution of programmable elements would comprise execution ofcontract programmable elements, and natural language elements may, ormay not, comprise legally binding contract language. Furthermore,external resources may additionally comprise contract participantresources.

As part of variations wherein the method is provided as part of amanagement platform, the method may be implemented in conjunction withtemplate libraries. In these variations, executable document objects andexecutable document object components, in addition to interaction schemaobjects and interaction schema object components, may be obtained fromthese template libraries and then configured for a desiredimplementation. In some implementations, methods that include templatelibraries may further include steps to build the template libraries;i.e. building a document template library and building an interactionschema template library. Alternatively, template libraries may beobtained from outside of the method, or developed through existingmethod steps. Steps to obtain and configure document and interactionschema, components may be performed over a user interface (UI), as shownin FIGS. 2, 3 and 4 , but may be accessed through other means (e.g.command line, an). As an alternative to creating objects and componentsfrom scratch, template libraries may include predefined componentsdependent on the template context. Additionally, as part of a templateimplementation, users may be enabled to create new templates or modifyexisting templates, by creating, removing, or modifying executable andnon-executable components of a given template, interaction schemaobjects, and document objects.

Block S110, which includes creating an executable document object,functions to create, configure, and store an executable document objectwith a computer-implemented system. That is to say, creating anexecutable document object configures executable components of thedocument object, integrates non-executable components appropriatelywithin the document object, and stores the document object (e.g. on acloud storage serve, mainframe, database, execution platform, etc.) suchthat the executable document object will or can be executed. As shown inFIG. 5 , in some variations, creating an executable document object maycomprise setting executable programmable elements within the executabledocument object S112, integrating natural language elements with theprogrammable elements S114, and establishing a state for theprogrammable elements S116.

Dependent on implementation, creating an executable document object S110may occur in several different ways. In one variation, creating anexecutable document object may occur by receiving data definition of theexecutable document object and its components and thereby creating theexecutable document object and all of its subcomponents. For example, anedited data file with defined code and natural language may be receivedas part of the document object). In another variation, creating anexecutable document object may be created and put together on a UI,wherein components may be stored, added, removed, or modified throughthe UI. This variation may be implemented with a template library,wherein library components may be added and modified as part of creatingan executable document object S110. Dependent on implementation,creating an executable document object S110 may include performing allsub-steps on a single platform (e.g. management platform), but mayalternatively include performing some, or all, sub-steps on distinctplatforms (e.g. programmable elements may be added through a UI after anatural language document created externally is imported onto theplatform). When performing on different computing platforms, the methodmay include communicating and coordinating the creation of theexecutable document object.

The executable document object may be any type of general, or specific,electronic document with executable components. Examples may include:electronic contracts, executable spreadsheets, markup texts, dynamicreporting documents, and the like. An executable document object maycomprise executable programmable elements and may include naturallanguage elements.

An executable document object preferably includes at least oneprogrammable element. Alternatively, the executable document object maynot include any programmable elements. Programmable elements function asthe dynamic programmable logic-based executable components, embeddedwithin the executable document object. Programmable elements maycomprise simple, or complex, functionalities; and thus for practicalreasons may differ in size from a single line representation of code tothousands of lines of code. For example, one programmable element mayupdate the value of a variable by copying the value from a source; asecond programmable element may comprise a media player, and a thirdprogrammable element may implement dynamic simulations based oninformation within the document object. Programmable elements may call,or interact, with other programmable elements as desired dependent onimplementation.

Execution of the document object may refer to execution of any number ofprogrammable element(s) within the document object. That is, executionof the document object may entail synchronous execution of one, or more,programmable elements within the document object; and/or execution ofone, or more, asynchronous programmable elements within the document object.

Executable document objects can include natural language elements.Alternatively, an executable document object may not include naturallanguage elements. Natural language elements may function as “text” ofthe document object. As used herein, natural language elements may refergenerally to any non-executable element within the document object. Forexample, natural language may be in English, or any other writtenlanguage, but may alternatively be in a coded language, encrypted form,machine language, or any other alternative form of “natural language”that can convey information. Additionally, natural language elements mayinclude rich media content, such as images, video, audio elements,charts, figures, and/or other non-executable elements.

Creating an executable document object S110 may include settingexecutable programmable elements within the executable document object.This may entail generating new programmable elements (e.g. creatingsource code) and/or extracting programmable elements from a source.Setting executable programmable elements functions to provide theexecutable logic for the executable document object. In variations thatinclude a template library, the setting executable programmable elementsmay include extracting programmable elements from a document template.Setting executable programmable elements may include incorporatingsingle programmable elements, or sets of programmable elements.

Extracting programmable elements from a document template may includechoosing a desired document template, and then choosing the desiredprogrammable element(s) included (or linked) to the document object tobe extracted.

In some variations, setting programmable elements may comprise somecombination of generating new programmable elements and extractingprogrammable elements from a source. In a template library example,setting programmable elements may comprise: generating a programmableelement and associating the programmable element with a documenttemplate. Generating the programmable element and associating theprogrammable element may be steps taken by a user. As part of a serviceimplementation of the method, generating a programmable element andassociating the programmable element with a document template may beactions taken by a vendor providing the service; and a user/customer maythen extract programmable elements from the document template asdesired.

In some variations, setting programmable elements may occur through agraphical user interface (GUI). In these variations, a user may‘drag-and-drop’ a preconfigured programmable element into the documentobject from a library of programmable elements. The library ofprogrammable elements may comprise a limited list of programmableelements within a specific document template, or may comprise anexpanded list of all library programmable elements. After setting theprogrammable elements, the programmable elements may then be modified(e.g. added removed or edited). In some variations, adding theseprogrammable elements may generate code within the document. A user maythen edit this code either manually, by modifying the code, throughmenu-driven options of the user interface, or through a command lineinterface.

Creating an executable document object S110 may include integratingnatural language elements with the programmable elements. Integratingnatural language elements may function to provide “readability” to theexecutable document object. Integration may include creating and storinga document object that has interspersed programmable and naturallanguage elements. This integration may take any desired form. In oneexample, integrating natural language elements may create a markupdocument. In a second example, integrating natural language may create aJSON file. The type of integration and document object created maydepend on desired implementation.

In variations, wherein the natural language is pre-generated, (e.g.previously included in a template document) integrating natural languagemay enable a user to edit the natural language. This may generallyinclude editing the integrated document object text, but dependent onthe type of natural language this may include adding or removing certainnatural language elements (e.g. adding a video file).

In variations that include a template library, integrating naturallanguage elements may include setting natural language elements from thelibrary. In some implementations, natural language elements may be“pre”-integrated with programmable elements in a document template. Inthese variations, setting programmable elements and integrating naturallanguage elements may comprise simultaneous or concurrent actions.Analogous to the addition of programmable elements, natural languageelements may also be taken from a document template. As part of a GUI,natural language elements may be added, removed, moved, and/or modifiedas desired.

Creating an executable document object S110 preferably includesestablishing a state for the programmable elements. Establishing a statefor the programmable elements functions to enable the execution of theprogrammable elements, and thus also the execution of the executabledocument object. In some variations, establishing a state comprisessetting the state of some and/or all the independent variables of eachprogrammable element. This may be performed in response to received userinput or machine/system input other form of input. Alternatively, someand/or all variables may have external associations such that they maybe set through other means. In variations that include a GUI,establishing a state for the programmable elements may occur through amenu-driven process wherein lists of available parameters may beprovided for the user to choose from. In some variations, the executabledocument object and/or programmable elements may have a static state(also referred to as “stateless”). In these variations, no state isgenerated and/or stored for the document object. Establishing a statefor the programmable elements of a stateless executable document maythus enable execution of the document without altering the state, orrequiring storage of the state, of programmable elements and documentobjects.

Block S120, which includes constructing an interaction schema object,functions to create a data resource object establishing logic flows thatdefine and control interactions between the document object and externalresources, thus setting up an external resource integration for aninteraction schema object. Constructing an interaction schema object mayinvolve defining the steps in an interaction schema for processing inputto or output from a programmable element. An interaction schemapreferably configures and manages integration through an API such as anAPI for services such as, but not limited to, cloud services (e.g.Google Cloud), a payment gateway (e.g. Stripe), a secure private server,a blockchain or distributed ledger system (e.g. an Ethereum-basedblockchain), a network-connected device (e.g. via an IoT platform API)and/or other APIs. An interaction schema object may be constructed foreach external resource interaction. Alternatively, multiple interactionschema objects may be constructed for each external source interaction.As shown in FIG. 6 , in some variations that include a template library,constructing an interaction schema object S120 may comprise associatingan external resource with the executable document object S122,generating an executable logic for the interaction schema from aninteraction schema template S124, determining a trigger type for atrigger S126, and instantiating the executable logic of the interactionschema S128.

The interaction schema preferably associates an external resource withthe executable document object. The external resource may comprise anyresource external to the document object and/or the platform thatmanages the document object. That is, dependent on the implementation,the external resource may be on or off the management platform, locallyor externally controlled and/or managed. The external resource may bedirectly connected (e.g. hard-wired) to the document managementplatform, or may be indirectly connected (e.g. over the internet).Dependent on the implementation external resources may be any private orpublic resource. Examples of external resources include: a blockchain, adistributed ledger, a private server, an API service (e.g., Stripe,Slack, etc.), repositories (e.g. Amazon S3, GitHub, etc.), files (e.g.CSV files and lookup tables), an application, network-connected device,a locally managed or cloud-based e-signature service, an audit log,local timer, local network notification system and/or any other type ofexternal resource.

Each interaction schema object comprises executable logic and a trigger,wherein activation of the trigger executes the executable logic. Theinteraction schema may comprise an inbound interaction schema (logicflow from an external resource to the document object), or an outboundinteraction schema (logic flow from the document object to the externalresource). Alternatively, an interaction schema may comprise both aninbound interaction schema and an outbound interaction schema. Theexecutable logic may be of any arbitrary complexity and comprise anynumber of steps as desired. The method may additionally includeconstructing multiple inbound and/or outbound interaction schemas, whichare then associated with an executable document object. Similarly, oneinteraction schema may be associated with multiple executable documentobjects.

Constructing an interaction schema object S120 preferably includesassociating an external resource with the executable document object. Insome variations, a single external resource is associated with eachinteraction schema object; alternatively multiple external resources maybe associated with a single interaction schema. Associating an externalresource with the executable object functions to setup the frameworksuch that user-provided information may enable interaction between theexternal resource and document object. The method steps of associatingan external resource may be unique to the specific external resource(e.g. many APIs have different security and connection protocols whichmust be used for interaction with that API). Associating an externalresource may thus include providing authentication details specific forthe external resource. In some variations that include a templatelibrary, the template library may include external resource-specificinteraction schema templates, wherein user-specific association detailsmay be added through a UI, command line interface (CLI) or otherinterface.

Constructing an interaction schema object S120 preferably includesgenerating an executable logic. The executable logic may function todefine business logic of the document object and/or the interactionbetween the document object and an external resource. Generating theexecutable logic may be dependent on implementation and the associatedexternal resource. In some variations, wherein the external resourceprovides integration tools, generating the executable logic may compriseobtaining the executable logic from the external resource (or otherthird party). In variations that include a template library, generatingan executable logic may comprise generating the executable logic fromthe interaction schema template for the desired API. Alternatively,generating an executable logic may comprise creating the executablelogic (e.g. coding). In these variations, the executable logic may beadded to the template library for future use as part of an interactionschema template.

The executable logic functionality may be dependent on the direction ofthe interaction schema, the associated external resource, and the typeof interaction between the document object and the external resource.Typical outbound interaction schema functionality includes actions on orby the external resource. For example, for an outbound interactionschema, the executable logic to a payment gateway account may call forthe payment gateway account (e.g. a Stripe account) to make payment. Ina second example, the executable logic to a blockchain may call forstorage of the document object or part thereof (e.g. a document objectstate) on the blockchain. Other examples of outbound interaction schemasmay include, but are not limited to: sending a notification or messageon an instant message platform (e.g. Slack) or via an email deliveryservice (e.g. SendGrid), generating an invoice on an accountingapplication, triggering a workflow on a robotic process automation (RPA)service, and triggering the logic of a blockchain or distributedledger-based smart contract.

Executable logic for inbound interaction schemas typically reportsevents. These events may then subsequently lead to execution ofprogrammable elements of the document object. In one example of aninbound interaction schema, the executable logic from an e-signatureservice may indicate to the document object that all signatories havesigned. In a second example, the executable logic from an informationservice (e.g. weather service, stock price service) may relay updatedinformation to the document object. Other examples of inboundinteraction schemas include: confirmation that a payment was made via apayment gateway, a delivery was recorded via a freight or courierservice, a data ‘oracle’ service, and/or other examples. Other examplesmay include services established specifically for the provision of datato the document object such as a timer, custom middleware, application,or API.

The interaction schema preferably includes a trigger, wherein theactivation of the trigger may function to initiate the executable logicof the interaction schema. Constructing an interaction schema objectS120 may include setting a trigger type for the trigger, wherein thetrigger type functions to set how a trigger is activated. Trigger typesmay be dependent on the interaction schema direction (e.g. inboundinteraction schema or outbound interaction schema), wherein othertrigger types may be independent of the interaction schema direction. Atrigger type may be an event, operation, action, process, transaction,or any similar type of occurrence that can happen on, or within, adocument management system, an external service, an application, asystem, on a blockchain/distributed ledger, an API, or other platform.One example of an independent trigger type is a time-based trigger (e.g.a trigger that activates at a specific time or at intervals). Anoutbound interaction schema trigger type may be an action trigger, suchthat once a specific document object action occurs (e.g. a programmableelement execution), the interaction schema is activated. An inboundinteraction schema trigger type may be an event trigger (e.g. webhook),wherein the interaction schema monitors for a specific external event toactivate. In some variations, the trigger is a Boolean which eitherdoes, or does not, initiate execution of the executable logic.Alternatively, the trigger may be graded, such that it is dependent on‘how’ the trigger is activated, execution of the executable logic maydiffer.

Constructing an interaction schema object 5120 may include instantiatingthe executable logic of the interaction schema. Instantiating theexecutable logic of the interaction schema functions to enable operationof the interaction schema object. Instantiating the executable logic mayinclude adding or linking necessary information such that executablelogic may successfully function with regards to the document object andthe associated external resource. In many variations, instantiating theexecutable logic may include adding/linking necessary credentials (e.g.,security login, authentication tokens, shared secrets, etc.) to enable auser, account, or entity to connect to the external resource. The typeof added/linked information may be unique to the user, to the potentialinteraction schema activity, and/or to the external resource(s).

In some variations, instantiating the executable logic of theinteraction schema object may include user interaction(s) receivedthrough a user interface, wherein the user is required to provide accessor other credentials for the external resource. Dependent onimplementation, the credentials may be requested in every interaction,or may be stored for automated access. For example, the executable logicthat is used to broadcast messages over Slack may include the user logininformation to connect to a Slack account. This login information may beobtained during an initial instantiation of the executable logic. Forvariations that include a management platform with a template library, auser may initially provide security and access information as part of aprofile on the platform. As part of choosing an interaction schematemplate with association to a specific external resource, the requireduser information may be directly instantiated in the executable logic.

Block S130, which includes bundling the interaction schema object withthe executable document object, functions to configure and store theexecutable document object and all interaction schemas associated withthe executable document object. In some variations, bundling creates andstores the interaction schemas and the document object as a single file.Alternatively, they may be stored as multiple files.

As shown in FIG. 7 , in some variations that include a template library,bundling may occur prior to creating an executable document object S110and constructing an interaction schema object S120. In these variations,block S130 may comprise bundling a document template with one or moreinteraction schema templates. In these variations, creating anexecutable document object would then entail creating an executabledocument object already bundled to a set of interaction schemas.Although potentially any interaction schema template may be bundled witha document template, bundling at the template level may enable efficientpackaging and utilization of interaction schema objects that arecommonly used with a particular document object type. That is, adocument template may be bundled with any number of interaction schematemplates that are typically used together. In this manner, interactionschema templates may be added, removed, or modified from any documenttemplate bundle. In some implementations of bundled templates, once auser has chosen a document template, a user may then (e.g. through a UIor CLI) choose and set up interaction schemas that have their associatedinteraction schema template bundled with the document template. As partof the user profile implementation, a user may then choose a bundledtemplate package dependent on a desired executable document object, andadd/remove/modify interaction schema templates associated with desiredexternal resources; wherein the user profile information may be used toautomatically instantiate the necessary interaction schema objects. Adocument template bundle may be configured and stored for reuse for agiven instance of a document type. A document template bundle may bestored in a library or repository for ease of reuse and deployment.

As part of a method for executable electronic document management, themethod may further include executable document actions, wherein theseactions may be in response to external events and/or in response toactions of the executable document object. As shown in the flowchartrepresentation of FIG. 8 , one variation of responses may be seen as aresponse to an external trigger leading to an inbound interaction schemato the element logic (e.g. a programmable element) of the documentobject, which may then trigger an outbound interaction schema leading toan action on, or within, some associated external resource and/or theexecutable logic of the document object or interaction schema object(s).

The method may include, in response to triggering an inbound interactionschema trigger: activating the executable logic of the inboundinteraction schema, initiating at least one programmable element of theexecutable document object, and updating the state of the executabledocument object. The inbound interaction schema response functions toinitiate execution of at least one programmable element within thedocument object, update the state of the document object via the inboundinteraction schema. In some implementations and situations, executionmay comprise execution of the document object. Inbound interactionschema trigger types may generally be any type of trigger type. In somevariations inbound interaction schema trigger types are event triggertypes (e.g. webhook), wherein the associated external resource ismonitoring for a specific event to initiate the trigger.

Block S210, which includes activating the executable logic of theinbound interaction schema, functions in activating the inbound workflowto the document object, in response to the trigger.

Block S212, which includes initiating at least one programmable elementof the executable document object, functions in executing at least oneprogrammable element of the document object. The programmable element(s)execution may be dependent on the inbound interaction schema. Forexample, an inbound interaction schema containing weather informationfor a weather interaction document object may execute programmableelements that include temperature-dependent variables. In anotherexample, an inbound interaction schema from an e-signature externalresource to a contract document object may initiate the execution of thecontract document object (e.g. when all contract signatories havesigned). In a third example, an inbound interaction schema from apayment gateway service containing a sale confirmation to a salesdocument object may initiate a to close the sale. In a fourth example,an inbound interaction schema from an identity or credentialverification service containing identity verification data (e.g. anaccess token or other data) may trigger executable logic within thedocument object or within another integrated resource such configuringan e-signature “surface area” or other functionality instantiated intothe document via one or more interaction schema steps. Doing so mayenable configuration of the e-signature service based upon the responsefrom the credentialing resource. In a discrete example, the e-signatureof the document may be conditioned via the executable logic of thedocument object and/or associated interaction schemas to conditionsignature functionality using the data returned from the credentialingservice.

In some variations, inbound and outbound interaction schema responsesmay include participation of a task management component, wherein thetask management component may be used to configure user intervention,operation, or action in an interaction schema such as manualconfirmation of triggering a payment on an external resource. In a sixthexample, as shown in FIG. 13 , in response to an inbound interactionschema from the e-signature, a programmable element may generate a stateobject and a contract event (e.g. a payment obligation). The payment, onan external system, may be approved as a task at the task managementcomponent. The payment transaction is performed through a paymentgateway API by transforming a payment obligation object via a connector.

Block S214, which includes updating the state of the executable documentobject, functions to set the state of the document object. Updating thestate of the executable document object S214 preferably occurs inconjunction with block S212. That is, the state of the document objectmay be updated whenever a programmable element is executed.Alternatively, updating the state of the executable document object S214may be independent of initiating at least one programmable element, ormay alternatively lead to initiating a programmable element. State maybe configured in any appropriate manner for retention.

The method may include, in response to triggering an outboundinteraction schema trigger: activating the executable logic of theoutbound interaction schema S220, and modifying the associated externalresource(s) S222. The outbound interaction schema response functions asan action on an external resource via the outbound interaction schema.Outbound interaction schema trigger types may generally be any triggertype. In some variations, inbound interaction schema trigger types areaction trigger types in response to distinct state changes of thedocument object (e.g. execution of the document object, document objectstate update).

Block S220, which includes activating the executable logic of theoutbound interaction schema, functions in activating an outboundworkflow from the document object to an external resource in response tothe trigger.

Block S222, which includes modifying the associated external resource,functions to perform an action on the external resource, or through theexternal resource. For example, an outbound interaction schema to aninstant message account (e.g. Slack), in response to a warning call froma weather interaction document object, may use the Slack account to senda weather warning to all subscribed members to the account. A distinctoutbound interaction schema to a blockchain system from the weatherinteraction document object may lead to modifying the blockchain stateby storing the new state of the weather interaction document objectand/or triggering a transaction through a call to a blockchain “smartcontract”.

In a general contract example for a contract document object, detectedconfirmation of signing of a contract can be used initiating variousoperations managed through the executable contract. For example, uponexecution of a contract document object between two people: an outboundinteraction schema, to a payment processor, may lead to a paymentprocessed from one user account to the other user account. The processedpayment may in turn trigger a payment confirmation event, leading to aninbound interaction schema, executing a ‘contract complete’ programmableelement. Updating the state of the contract document to ‘completion’ mayin turn trigger an outbound action(s) to private APIs for thecontracting parties. These outbound actions may then provideconfirmation messages to the users and provide other functionalities onthe private APIs (e.g. copy the contract document history on a localserver on the private API).

3. System

As shown in FIG. 9 , a system for management of digital dynamicdocuments comprising: a document management system 110, used forcreating, editing, and managing electronic documents; a repositorysystem 120, used for storing electronic documents and associatedcomponents; a templating system 130, used for creating, adding,removing, and modifying templates, and an execution engine 140.Additional and/or alternative components may be used in variations. Thesystem may function to enable formation, execution, and configuration ofelectronic documents, including specification of programmable elements,i.e. addition, removal, and modification of the programmable elements.Furthermore, the system may enable and define interaction with externalresources; through creation, association, and packaging of interactionschemas with the electronic document (i.e. document package), whereinthese interaction schemas control interaction between the electronicdocument and external APIs.

The system may be implemented in any general manner for electronicdocument management and execution, but may be particularly useful forimplementation of the method as described above. In some variations, thesystem may be implemented as a local platform for a single user, orlocal network user implementation. In another variation, the system maybe implemented as a service wherein users may access the system remotely(e.g. cloud service).

In some variations, the system may be implemented for specializedelectronic documents. The system for specialized documents may includeadditional components, additional functionalities further, and/oradditional optimizations in accordance with the type of specializedelectronic document. For example, a system specialized for contractelectronic documents may further include components that enable userinteraction, negotiation, and optimizations regarding purchases andsales. Other examples may include systems specialized for: policydocuments, purchase orders, letters of credit/credit documents,statements, planning documents, financial records, and spreadsheets.Dependent on implementation, system components, functionalities, andoptimizations may be added, removed, or added, as desired.

An electronic document may take any suitable form or structure asdesired. In many variations, the electronic document may comprise, atleast partially, of machine-readable/computable components, i.e.programmable components. Additionally, the electronic document maycomprise, at least partially, of language-based natural language (NL)components. The electronic document may have any general structure. Insome variations, the electronic document may have class-like structureswith clauses. Document clauses may be composed of machine-readableprogrammable clauses and NL clauses. Clause logic may be written in anexpression language with limited expressiveness, or any degree ofexpressiveness, allowing conditional and bounded iterations.

In some variations, the electronic document and its representations(e.g. template documents) may be bundled with interaction schemas (i.e.a document package). The document package comprises the electronicdocument and any number of inbound interaction schemas and/or outboundinteraction schemas, wherein each interaction schema defines andcontrols interaction between the electronic document and an externalAPI.

The system of a preferred embodiment includes a document managementsystem 110. The document management system 110 may include a documenteditor, a template library, and a user dashboard. The documentmanagement system 110 functions to enable users to edit, form, manage,and analyze electronic documents. In contract specialized variations thedocument management system 110 may further enable user interactions(e.g. negotiation, decision making, contract signing).

Additionally, in many variations, the document management system 110 maybe used to define and configure external API interactions. Through thedocument management system 110, a user may add, remove, edit, or manageinteraction schemas between the electronic document and external APIs.As shown in FIG. 10 , the document management system 110 mayadditionally enable packaging of inbound interaction schemas andoutbound interaction schemas with the electronic document, creatingdocument packages.

The document management system 110 may include a template library. Thetemplate library functions as a relevant library of templates for userimplementation. Libraries may be scoped for user accounts. A useraccount may have multiple libraries. Libraries may contain documenttemplates and/or interaction schema templates. That is, the templatelibrary organizes templates by associations, enabling quick accesses topotentially relevant templates for a user. Templates may haveuser-defined ‘tags’, keywords or similar to enable users to search,label, and configure templates. In some variations, the template libraryenables the use of search terms to find a desired template.Additionally, once a document template has been chosen, the templatelibrary may present commonly associated interaction schema templatesthat can be used and/or are typically used with the document template.

In some variations, the template library may implement associationand/or learning models to track which interaction schemas (orinteraction schema templates) are used with a particular executabledocument (or document template). In these variations, the templatelibrary may leverage this information to provide an updated list of‘typically used’ interaction schemas.

The document management system 110 may include a document editor. Thedocument editor functions to enable editing of electronic documents andassociated subcomponents. The document editor may provide a GUI for userinteraction. The document editor may enable importing saved documentsfor editing, or importing document templates for creating new documents.The document editor may enable the addition of components through manualtext editing of documents, and/or importing components. An editor mayprovide additional functionality that may be beneficial for certaindocument types such as commenting, collaborative editing, and‘redlining’.

Components may be imported directly from the repository (e.g. a distinctprogrammable component function), imported from other executabledocuments, or imported as part of a template from the template library.In some variations, once programmable components and/or natural languagecomponents are imported (either directly or through a template), a textrepresentation of the component may be generated (e.g. code forprogrammable components and human-readable text for natural languagecomponents). These text representations may be directly edited in thedocument editor as desired. In some variations, context-based windowsmay additionally, or alternatively, be used to edit importedprogrammable components and/or natural language elements.

The document editor may additionally enable adding, editing,configuring, and/or removing interaction schemas from the document.Interaction schemas may be edited as distinct objects that are thenlinked to the electronic document. Alternatively, interaction schemasmay be stored within the electronic document. Interaction schemas may beadded from an interaction schema template, wherein a text-based coderepresentation of the interaction schema logic may be generated. Coderepresentations may be directly edited in the document editor asdesired. In some variations, context-based windows may additionally, oralternatively, be used to define and/or select variations/instantiationsof the interaction schema. In other variations, a document editor mayform a component of an integrated development environment (IDE) fordeveloping electronic documents including interaction schemas. In oneimplementation, an expression language may be used to define the logicof the interaction schema between steps. For example, JSONata totransform JSON generated by an object and transformed to an action on anAPI. FIG. 3 shows one implementation through a user interface for atrigger, using a JSONata transform, HTTP request.

The dashboard may function as an interface that provides documentinformation to the user. Additionally, the dashboard may provide toolsfor analysis of the electronic document and/or document package. Thedashboard may be a configurable interface. As desired, the dashboard mayprovide relevant information (e.g. as configured by the user) to theuser in some desired interval (e.g. periodic updates, threshold updates,document state change updates).

In some variations, the dashboard may further enable users to performanalytics on electronic documents. Through the dashboard, individualelectronic documents, and/or groups of electronic documents may beanalyzed for general statistical information (e.g. average, mean, mode),trend analysis (e.g. linear regression, power laws), and data modelingas well as predictive, prescriptive, and descriptive analytics.

The repository system 120 of a preferred embodiment functions to storeelectronic documents and document related data. Document related datamay include all of the data pertaining to an electronic document.Document related data may include (but is not limited to) the documenttemplates, wherein the document templates comprise template text and/ortemplate logic and any associated interaction schemas.

The repository system 120 may comprise any type of database,cloud-storage, private storage device (e.g. local hard drive), which maybe either locally or remotely hosted. The repository system 120 ispreferably accessible from the document management system 110. Therepository system 120 may be a multi-tenant cloud-based system, alocally hosted system, on or as part of a peer-to-peer network (e.g.utilizing a distributed file system such as InterPlanetary File System),or take the form of any suitable data storage system. In oneimplementation, a distributed version control system (e.g. git) is usedas a component of the repository system 120.

The templating system 130 of a preferred embodiment functions to bindnatural language text to executable programmable logic in a reusablemanner. The templating system 130 may take any suitable form. In onevariation, the templating system 130 may comprise three components: atemplate grammar, a template model, and the template logic. Alternativecomponents and structures may be used in variations.

The template may consist of natural language text that identifiesdata-oriented variables (e.g. price, date, etc.).

The template model may provide a framework for categorizing thevariables and the components of the business context that “activate” theelectronic document. In some variations, the template model can mirroror otherwise map to an object model (e.g. an object model of ablockchain network). In alternative variations, the template model maybe used with text and logic bound together using a mark-up language, alanguage-independent format (e.g. JSON), and/or in a formalrepresentation (e.g. a programming language).

The template model may then be embedded within, or linked to theelectronic document. A programmable element within a document may beexecuted by exposing data to the programmable element (e.g. events fromexternal resources such as freight being shipped, delivered, signed-foretc.). These events may be routed to the template so that the templatecan take appropriate action. In one implementation, events may bestructured as a request-response model. FIG. 11 depicts one variation ofthe template model, along with request and response types. In thisvariation of the template model, a template request transaction definesthe data that the template needs to receive from external sources. Thetemplate response transaction may define the data that the template willreturn when it receives a template request. FIG. 12 depicts an alternatevariation alongside the request and response. In this variation, theevent may lead to an additional response or external operation. In oneexample, the external operation may be an event confirmation (e.g.performed by a task management system). In an electronic contractimplementation, once an event has occurred, the task management systemmay send/seek confirmation from the contract participants to perform anoperation such as triggering steps configured in an interaction schemawithout that occurring through execution of the interaction schemawithout user intervention.

In some variations, the system may further include a task managementcomponent. A task management subsystem/component may also form part of amanagement system. The task management component preferably exposescontract events and external actions to the user through the managementsystem. In a preferred embodiment, the task management componentaggregates and collates events scoped by document for display to the enduser. In electronic contract implementations, these events may be pulleddirectly from the same source as the audit log. The task managementcomponent may expose data to a user of the system and method as adashboard or series of dashboards. In some variations, a multiplicity ofdata visualization tools may be used to provide analytics and other datato users on the status of tasks. For example, data exposed in contractevent objects may be used to show changes to the status of contractobligations over time, time elapsed since obligations became effective,overdue obligations, obligations that need performing on an externalresource, and/or other exemplary changes to the status.

The task management component preferably enables users to interact withcontract events and other forms of contract action. For example, aconfigured action such as a payment may be ‘queued’ as a task requiringuser initiation (e.g. a signatory to a contract or a user within thesignatory's organization scope), such as approval, before outboundinteraction schema steps are triggered to execute a payment transactionon an external resource such as a payment gateway. This enables thestate of a contract to be computed, including contract operations onexternal systems, without triggering execution on the external systemdirectly from a programmable component. Exceptions (e.g. configuredparameters such as payment values) may be defined to automaticallyapprove/execute suitably configured operations. Conditionals of anyarbitrary complexity may be supported.

The execution engine 140, of a preferred embodiment, functions toexecute programmable logic of electronic documents. The execution engine140 preferably acts upon incoming requests to the logic of a documenttemplate instance, executing the functions of the logic, emitting aresponse, updating the document state, and emitting any other objects orevents as defined by the logic and/or interaction schema.

The execution engine 140 may handle a variety of input types. Examplesof input types include: data input accessed over a programmaticinterface (e.g., a REST API, GraphQL API, SOAP API, etc.), simplemathematical transformations of the data from those APIs, eventnotifications, data from various blockchain/distributed ledgers, datafrom the execution of programmable components of the electronicdocument, off-chain or on-chain, and/or other various sources.

The execution engine 140 may be designed to be embeddable across awide-variety of form factors: web, middleware, SaaS (Software as aService), on a blockchain or distributed ledger, or any other suitableruntime environment. The execution engine 140 may take any suitable formof computing/runtime environment for executing programmable elementswithin documents. The execution engine 140 may be run in a sharedexecution environment such as public, dedicated, or private cloudenvironment, on a shared server, on a peer-to-peer network, or otherappropriate execution environment. In one variation, the executionengine 140 may take the form of an interpreter, virtual machine (VM) ormay form part of one. A virtual machine may be web-based, cloud-based,run on a cluster, or in any other suitable environment. In somevariations, the execution engine 140 may be used within, or on, ablockchain or distributed ledger system. Alternatively, an executionengine 140 may be embedded within a node on a blockchain or distributedledger system. A node on a blockchain system is a device on a blockchainor distributed ledger network, which preferably serves to process anindividual copy of the blockchain or ledger. For a contract electronicdocument, the nodes of the blockchain or distributed ledger system maymaintain the document state globally, across participants, andfacilitate computation of state consensus.

The results of logic execution (e.g. the execution of a JSON serializedobject) may include, but are not limited to: outputting/logging detailsof the programmable component that was executed (name, version, SHA256hash of element data); generation of an incoming request object; andgeneration of an output response object. In some variations, thedocument state may be maintained at the document level by optionallyattaching a document to a state object, giving the logic of the documentread and write access to the document state. Additional and/oralternative data, objects, and metadata may be included. Alternatively,document state may be maintained at the element level (e.g. by theprogrammable component).

Execution of the programmable component may also emit event objects inaddition to response object(s). Event objects may be emitted to anexternal storage system (e.g. a blockchain), stored on a document statesystem, or otherwise used as an appropriate medium for the persistencecomponent. For example, a programmable component within a contractelectronic document may emit an obligation object, which can be mappedto external resource script function calls (e.g. to transition the stateof a distributed ledger or blockchain network or other resource such asan application).

The execution engine 140 may further comprise a compiler. The compilerfunctions to generate code from the document programmable logic forexecution. The programmable logic may be in any suitable language,including a domain specific language such as for contracts (e.g. aprogramming or markup language). Prior to execution, the compiler maygenerate code for execution from the template, using the documentprogrammable logic. The document programmable logic may be in anysuitable language. The generated code for execution may be for anydesired suitable platform. The compiler may also cross-compile togenerate executable code for any other platform (e.g., a given BDLsystem, virtual machine, a microcontroller of a resource constraineddevice such as an IoT device, etc.). In some variations, the logic ofthe programmable element may be compiled down to, or otherwise,delegated to an alternative runtime for execution. For example, thecompiler in the system and method may generate binary code/bytecode fora blockchain, distributed ledger, and/or an electronic contract system.

The compiler may take any suitable form. Alternatively, any suitablealternative architecture with similar functionality may be used insteadof the compiler. In one variation, the compiler may include: a parser,wherein the parser parses contract logic from a syntax tree to anexecutable syntax tree; a type checker, that checks the validity of theprogrammable component logic against the template model logic and checksthe validity of the document against the template grammar and typingrules; a translation from the contract logic syntax tree to calculus(i.e., optimizer), that “de-sugars” syntactic sugar to improvecode-generation from a simpler calculus; and a code-generator fromcalculus to a target language. The compiler may further includetarget-specific runtime libraries (e.g. JavaScript operation to create anew electronic document). In addition, user-level standard libraries,for core operations (e.g. math libraries) may also be included.

4. System Architecture

The systems and methods of the embodiments can be embodied and/orimplemented at least in part as a machine configured to receive acomputer-readable medium storing computer-readable instructions. Theinstructions can be executed by computer-executable componentsintegrated with the application, applet, host, server, network, website,communication service, communication interface,hardware/firmware/software elements of a user computer or mobile device,wristband, smartphone, or any suitable combination thereof. Othersystems and methods of the embodiment can be embodied and/or implementedat least in part as a machine configured to receive a computer-readablemedium storing computer-readable instructions. The instructions can beexecuted by computer-executable components integrated with apparatusesand networks of the type described above. The computer-readable mediumcan be stored on any suitable computer readable media such as RAMs,ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives,floppy drives, or any suitable device. The computer-executable componentcan be a processor but any suitable dedicated hardware device can(alternatively or additionally) execute the instructions.

In one variation, a system comprising of one or more non-transitorycomputer-readable mediums storing instructions that, when executed bythe one or more computer processors, cause a computing platform toperform operations comprising those of the system or method describedherein such as: creating an executable document object; constructing aninteraction schema object; and bundling the interaction schema with theexecutable document object, and optionally performing actions inresponse to triggering an inbound interaction schema trigger ad/oroptionally performing actions in response to triggering an outboundinteraction schema trigger.

FIG. 12 is an exemplary computer architecture diagram of oneimplementation of the system. In some implementations, the system isimplemented in a plurality of devices in communication over acommunication channel and/or network. In some implementations, theelements of the system are implemented in separate computing devices. Insome implementations, two or more of the system elements are implementedon the same devices. The system and portions of the system may beintegrated into a computing device or system that can serve as or withinthe system.

The communication channel 1001 interfaces with the processors1002A-1002N, the memory (e.g., a random access memory (RAM)) 1003, aread only memory (ROM) 1004, a processor-readable storage medium 1005, adisplay device 1006, a user input device 1007, and a network device1008. As shown, the computer infrastructure may be used in connectingdocument management system 1101, repository system 1102, templatingsystem 1103, execution engine 1104, and/or other suitable computingdevices.

The processors 1002A-1002N may take many forms, such CPUs (CentralProcessing Units), GPUs (Graphical Processing Units), microprocessors,ML/DL (Machine Learning/Deep Learning) processing units such as a TensorProcessing Unit, FPGA (Field Programmable Gate Arrays, customprocessors, and/or any suitable type of processor.

The processors 1002A-1002N and the main memory 1003 (or somesub-combination) can form a processing unit 1010. In some embodiments,the processing unit includes one or more processors communicativelycoupled to one or more of a RAM, ROM, and machine-readable storagemedium; the one or more processors of the processing unit receiveinstructions stored by the one or more of a RAM, ROM, andmachine-readable storage medium via a bus; and the one or moreprocessors execute the received instructions. In some embodiments, theprocessing unit is an ASIC (Application-Specific Integrated Circuit). Insome embodiments, the processing unit is a SoC (System-on-Chip). In someembodiments, the processing unit includes one or more of the elements ofthe system.

A network device 1008 may provide one or more wired or wirelessinterfaces for exchanging data and commands between the system and/orother devices, such as devices of external systems. Such wired andwireless interfaces include, for example, a universal serial bus (USB)interface, Bluetooth interface, Wi-Fi interface, Ethernet interface,near field communication (NFC) interface, and the like.

Computer and/or Machine-readable executable instructions comprising ofconfiguration for software programs (such as an operating system,application programs, and device drivers) can be stored in the memory1003 from the processor-readable storage medium 1005, the ROM 1004 orany other data storage system.

When executed by one or more computer processors, the respectivemachine-executable instructions may be accessed by at least one ofprocessors 1002A-1002N (of a processing unit 1010) via the communicationchannel 1001, and then executed by at least one of processors1001A-1001N. Data, databases, data records or other stored forms datacreated or used by the software programs can also be stored in thememory 1003, and such data is accessed by at least one of processors1002A-1002N during execution of the machine-executable instructions ofthe software programs.

The processor-readable storage medium 1005 is one of (or a combinationof two or more of) a hard drive, a flash drive, a DVD, a CD, an opticaldisk, a floppy disk, a flash storage, a solid state drive, a ROM, anEEPROM, an electronic circuit, a semiconductor memory device, and thelike. The processor-readable storage medium 1005 can include anoperating system, software programs, device drivers, and/or othersuitable sub-systems or software.

As used herein, first, second, third, etc. are used to characterize anddistinguish various elements, components, regions, layers and/orsections. These elements, components, regions, layers and/or sectionsshould not be limited by these terms. Use of numerical terms may be usedto distinguish one element, component, region, layer and/or section fromanother element, component, region, layer and/or section. Use of suchnumerical terms does not imply a sequence or order unless clearlyindicated by the context. Such numerical references may be usedinterchangeable without departing from the teaching of the embodimentsand variations herein.

As a person skilled in the art will recognize from the previous detaileddescription and from the figures and claims, modifications and changescan be made to the embodiments of the invention without departing fromthe scope of this invention as defined in the following claims.

1-20. (canceled)
 21. A method comprising: creating an executable agreement clause by: generating programmable clauses comprising programmable logic; and establishing a state for each programmable clause by setting values for one or more variables of each programmable clause; and constructing one or more logic flows associated with the executable electronic document, wherein each logic flow comprises executable logic and wherein each logic flow, when executed, produces at least one value associated with the one or more variables of a programmable logic clause.
 22. The method of claim 21, wherein at least one logic flow comprises an inbound logic flow triggered by a webhook.
 23. The method of claim 21, wherein at least one logic flow is an outbound logic flow that includes an action trigger that is activated with a state change of a programmable clause.
 24. The method of claim 23, wherein the action trigger comprises execution of the programmable clause.
 25. The method of claim 21, wherein constructing the one or more logic flows further comprises instantiating necessary credentials such that the one or more logic flows can access a resource associated with the at least one value.
 26. The method of claim 25, wherein instantiating the necessary credentials comprises using information from a user profile associated with the credentials to enable access to the resource.
 27. The method of claim 21, wherein creating the executable agreement clause comprises generating an electronic document comprising the executable agreement clause.
 28. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors, cause a computing platform to perform operations comprising: creating an executable agreement clause by: generating programmable clauses comprising programmable logic; and establishing a state for each programmable clause by setting values for one or more variables of each programmable clause; and constructing one or more logic flows associated with the executable electronic document, wherein each logic flow comprises executable logic and wherein each logic flow, when executed, produces at least one value associated with the one or more variables of a programmable logic clause.
 29. The non-transitory computer-readable medium of claim 28, wherein at least one logic flow comprises an inbound logic flow triggered by a webhook.
 30. The non-transitory computer-readable medium of claim 28, wherein at least one logic flow is an outbound logic flow that includes an action trigger that is activated with a state change of a programmable clause.
 31. The non-transitory computer-readable medium of claim 30, wherein the action trigger comprises execution of the programmable clause.
 32. The non-transitory computer-readable medium of claim 28, wherein constructing the one or more logic flows further comprises instantiating necessary credentials such that the one or more logic flows can access a resource associated with the at least one value.
 33. The non-transitory computer-readable medium of claim 32, wherein instantiating the necessary credentials comprises using information from a user profile associated with the credentials to enable access to the resource.
 34. The non-transitory computer-readable medium of claim 28, wherein creating the executable agreement clause comprises generating an electronic document comprising the executable agreement clause.
 35. A system comprising: memory with instructions encoded thereon; and one or more computer processors that, when executing the instructions, are caused to perform operations comprising: creating an executable agreement clause by: generating programmable clauses comprising programmable logic; and establishing a state for each programmable clause by setting values for one or more variables of each programmable clause; and constructing one or more logic flows associated with the executable electronic document, wherein each logic flow comprises executable logic and wherein each logic flow, when executed, produces at least one value associated with the one or more variables of a programmable logic clause.
 36. The system of claim 35, wherein at least one logic flow comprises an inbound logic flow triggered by a webhook.
 37. The system of claim 35, wherein at least one logic flow is an outbound logic flow that includes an action trigger that is activated with a state change of a programmable clause.
 38. The system of claim 37, wherein the action trigger comprises execution of the programmable clause.
 39. The system of claim 35, wherein constructing the one or more logic flows further comprises instantiating necessary credentials such that the one or more logic flows can access a resource associated with the at least one value.
 40. The system of claim 39, wherein instantiating the necessary credentials comprises using information from a user profile associated with the credentials to enable access to the resource. 